Security of Surveillance Media

ABSTRACT

A media device receives a domain key from a service provider. The media device further encrypts media with a media key and encrypts the media key with the domain key to form an encrypted media token: the protected media key is encapsulated in an encrypted media token. The service provider may then receive the encrypted media token and one or more receiving entity identifiers relating to a receiving entity and ascertain whether the receiving entity is entitled to access media from the media device. If the receiving entity is entitled to access media from the media device, the service provider decrypts the cryptographic media token using the domain key to obtain the media key and providing the media key to the receiving entity. As such, an authenticated receiving entity may obtain the media key necessary to decrypt the media. Moreover, there is no requirement for any intermediate entity to have similar access and thus the encryption provided by the media key is in place throughout the transport of the media from media device to receiving entity.

FIELD

The present disclosure relates to the security of media generated bymedia device, such as a surveillance device. In particular, but notexclusively, it relates to ensuring confidentiality of media generatedby a surveillance camera.

BACKGROUND

Many video surveillance systems protect generated surveillance mediacontent during transport between elements of the system. For example,where a camera generates a media stream for view at a remote device,confidentiality of the media is enforced in transport of the mediastream between elements of the system, such as between the camera,remote device and any intermediate devices though which the media streamis transported.

As a consequence, outside of secure communication phases between systemelements, there is often not protection enforcement and the mediacontent is actually unprotected, vulnerable and can be disclosed. Accesscontrol with suitable policy management is not always or weaklyimplemented on one or more elements of the system, meaning that:unprotected media content can be accessed without authorisation inelements without effective access control or monitoring; media contentis unprotected and vulnerable when access control or monitoring at anyelement is hacked or otherwise bypassed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic illustration of a system for implementing apreferred embodiment;

FIG. 2 is the schematic illustration of FIG. 1 with additionalinformation representing processing steps at each entity;

FIG. 3 is a process diagram showing the process of a preferredembodiment; and

FIG. 4 shows a hardware infrastructure for implementing a preferredembodiment.

DETAILED DESCRIPTION OF THE DRAWINGS

In overview, a method in accordance with the disclosure comprisessecuring media generated by a media device with a media key andprotecting the media key with a domain key to form an encrypted mediatoken. When a receiving entity wishes to access the media, a trustedservice provider can authenticate the receiving entity and decryptencrypted media token to retrieve the media key for use by the receivingentity to decrypt the media. In this way, the media can be protected bythe media device which generates it without being subsequently decrypteduntil it is present at an authorised receiving entity. Intermediateentities are not required to have access to the decrypted media. Thedisclosure further provides a computer readable medium and a systemconfigured to carry out this method.

In some aspects of the disclosure a method for securing media content ina network comprising the following steps is provided: A media devicereceives a domain key from a service provider. The media device furtherencrypts media with a media key and encrypts the media key with thedomain key to form an encrypted media token: the protected media key isencapsulated in an encrypted media token. The service provider may thenreceive the encrypted media token and one or more receiving entityidentifiers relating to a receiving entity and ascertain whether thereceiving entity is entitled to access media from the media device. Ifthe receiving entity is entitled to access media from the media device,the service provider decrypts the cryptographic media token using thedomain key to obtain the media key and providing the media key to thereceiving entity. As such, an authenticated receiving entity may obtainthe media key necessary to decrypt the media. Moreover, there is norequirement for any intermediate entity to have similar access and thusthe encryption provided by the media key is in place throughout thetransport of the media from media device to receiving entity.

In some embodiments, the media key is generated at the media device.Alternatively, the media key may be received by the media device from anexternal source, such as the service provider. The media key may be, forexample, randomly generated.

Optionally, the domain key is associated with a domain defining one ormore media devices within the network. Thus, the domain key may becommon to more than one media device. A given media device may be addedto or removed from a domain over time, allowing control over access tomedia from that media device through the process of authenticating areceiving entity. The receiving entity may be authenticated before thestep of ascertaining whether the receiving entity is authorised toaccess media from media devices within the domain associated with thedomain key.

The media device may receive the domain key from the service provider ina form encrypted using one or more media device identifiers. In thismanner, the service provider may ensure security of the transmission ofthe domain key to the media device.

The encrypted media token may comprise metadata associated with thedomain key. The protected media key is in that case encapsulated in theencrypted media token with metadata. For example, this metadata mayidentify the domain with which the domain key is associated or may insome other way allow the domain key to be identified. This can assistthe service provider in locating the domain key to be used to decryptthe encrypted media token.

In some embodiments, the media device transmits the encrypted mediatoken to the receiving entity and the service provider receives theencrypted media token from the receiving entity. For example, theencrypted media token may be transmitted to the receiving entitytogether with the media itself. In other examples, the encrypted mediatoken may be transmitted to the receiving entity in an out-of-bandcommunication, e.g. separately to the media. The encrypted media tokenmay be transmitted directly from the media device to the receivingentity or may be transmitted via one or more intermediate entities.

The service provider may receive the encrypted media token in a formencrypted using one or more receiving device identifiers. Alternativelyor additionally, the service provider may provide the media key to thereceiving entity in a form encrypted using one or more receiving deviceidentifiers. This approach can help to secure communication between thereceiving entity and the service provider.

One or both of the media key and domain key may be changed periodically.In this manner, security can be increased. Changing the media key or thedomain key may cause regeneration of the encrypted media token. Forexample, the media stream may comprise data packets and each data packetmay be encrypted using the media key prior to transmission from themedia device. If the media key is changed, e.g. after a pre-determinedlength time or after a pre-determined number of packets, then subsequentpackets of the same media stream are encrypted using the updated mediakey.

The media may comprise audio and/or visual content. The visual contentmay comprise video or one or more still images. The media may furthercomprise metadata. Such metadata could include, for example, an alarmindication designed to alert a user. The media may be streaming media.The media may be generated in real time by the media device. The mediadevice may comprise a camera. For example, the media device may be asurveillance camera such as a mobile surveillance camera. The mediadevice may be a drone, robot or wearable camera, for example. The mediadevice may be, but is not limited to, any other device capable ofprocessing or generating media.

In some aspects of the disclosure, there is provided a computer readablemedium comprising computer executable instructions for carrying out themethod of the aspects described above. Moreover, further aspects of thedisclosure provide a system configured to carry out these methods.

In some aspects of the disclosure there is provided a system forsecuring media content in a network comprising a media device and aservice provider. The media device is configured to: receive a domainkey from the service provider; and encrypt media with a media key andencrypting the media key with the domain key to form an encrypted mediatoken. The service provider is configured to receive the encrypted mediatoken and one or more receiving entity identifiers relating to areceiving entity; ascertain whether the receiving entity is entitled toaccess media from the media device; and, if the receiving entity isentitled to access media from the media device, decrypt the encryptedmedia token using the domain key to obtain the media key and provide themedia key to the receiving entity. Optional features of the method mayalso apply to the system. The system may further comprise the receivingentity. The receiving entity may be configured to decrypt the mediausing the media key received from the service provider.

Some specific embodiments are now described by way of illustration withreference to the accompanying drawings.

With reference to FIG. 1, a system is illustrated which comprises acamera device 11, one or more intermediate devices 20 and a receivingentity 30. The camera device is a media device which can generate mediato be received by the receiving entity 30. The media generated by thecamera 11 may be transmitted to the receiving entity 30 via the one ormore intermediate entities 20.

The camera device 11 may be part of any fixed or mobile surveillancesystem, such as a drone, robot or wearable device. In general it may beany device capable of processing or generating media content. Theintermediate entities 20 may be any network element capable of passingon network traffic, while the receiving entity 30 could be any suitabledevice for playback or processing of media. The receiving entity 30 maybe located at a surveillance control room or any other desired location,and may be fixed or portable. The receiving entity 30 may, for example,be a network-enabled end-user device such as a laptop, personalcomputer, tablet computer, smartphone or similar.

Also shown as part of the system of FIG. 1 is a license provisioningservice 40. This acts as a service provider and may communicate with apolicy manager 50. There is also shown a secrets provision service 60,which may optionally be provided to communicate with camera device 11and receiving entity 30.

The license provision service 40, policy manager 50 and secretsprovision service 60 may act in concert as a service provider. Each ofthem may be implemented as a cloud-based service or may be implementedon defined physical devices, such as a server.

In general, each of the elements illustrated in FIG. 1 may beimplemented on one or more computing devices, further details of whichare set out below with reference to FIG. 4.

The operation of the system of FIG. 1 can be understood with referenceto FIGS. 2 and 3. FIG. 2 shows the system of FIG. 1 with additionalreference numerals identifying communication within or between systemelements associated with process steps described below. This numberingin FIG. 2 is associated with paragraph numbers “1” to “10” below. FIG. 3is a process diagram providing further exposition of the certain processsteps and illustrating these in one possible sequential order.

1—At step s31, the camera 11 is configured with device unique secrets.There are one or more identifiers associated with the camera 11. Thosesecrets can be software or hardware based. They can be pre-provisionedat manufacturing time or over-the-air as shown as in FIG. 2, option 1 dfrom the secret provisioning service 60.

2—The camera is associated with a domain. This domain may connect orassociate the camera with the area it covers. At step s32, a domain keymay be generated for the domain by the license provisioning service 40.At step s34, which may occur during installation of camera 11, theunique domain key is supplied over-the-air from the license provisioningservice 40. This domain key is securely protected when transmitted tothe camera 11 using available device unique secrets. When the camera isinstalled in a new area or the existing area is split into new domain, anew unique domain key is supplied to the camera.

3—The camera 11 may generate a media key at step s35 used to encryptmedia generated by the camera at step s36. At step s37, this media keyis protected using the unique domain key and an encrypted media token isgenerated. The encrypted media token comprises the protected media keyand additional metadata. Any relevant information may be recorded in themetadata, such as information identifying the domain associated withcamera 11. Since the media is encrypted within the camera 11, it isprotected as it leaves the camera 11 to be transmitted elsewhere. Forexample, at step s38, the media encrypted by the media key istransmitted to the receiving entity 30. As can be seen in FIG. 2, thistransmission may occur via one or more intermediate entities 20. At steps29, the encrypted media token is also transmitted to the receivingentity 30. Depending on the streaming format, the encrypted media tokencan be transmitted either embedded in the protected camera media contentor with an out-of-band channel.

4—The receiving entity 30 may be configured with entity unique secretsat step s33. These act as one or more identifiers associated with thereceiving entity. The secrets can be software or hardware based. Theycan be pre-provisioned at manufacturing time or over the air asillustrated in FIG. 1, option 4 d from the secret provisioning service60.

5—Following step s39 described above, the receiving entity has receivedthe encrypted media token from the camera 11. If necessary, it mayextract this token from the media stream. In some alternatives, it willobtain it from an out-of-band channel. The receiving entity 30 thenprovides the encrypted media token to the license provisioning service40 at step s40. This is provided in the form of a cryptographicchallenge secured with entity unique secrets. This cryptographicchallenge is used to authenticate the receiving entity 30.

6—The license provisioning service 40 verifies the cryptographicchallenge which authenticated the receiving entity 30 in the previousstep 5, and extracts the encrypted media token. The license provisioningservice 40 identifies the domain from the metadata encapsulated in theencrypted media token. It may then confirm whether the receiving entityis authorised to access media from the camera 11. If receiving entity 30is authorized to access this domain by the policy manager 50, thelicense provisioning service 40 extracts the media key from theencrypted media token using the domain key at step s41. The licenseprovisioning service 40 then generates an encrypted entity tokenencapsulating the media key with relevant usage rules. The encryptedentity token is protected using the entity unique secrets known to thereceiving entity 30, rather than the domain key not known to thereceiving entity 30, and is provided back to the receiving entity 30 atstep s42.

7—The receiving entity 30 then verifies the encrypted entity tokenreceived from the license provisioning service 40. The receiving entity30 may then extract the media key and can therefore decrypt theprotected camera media content according to the related usage rules atstep s43. The resulting unprotected camera media content can be accessedand/or processed by the receiving entity.

8—As an option and in order to improve protection of camera mediacontent, the media key can be changed periodically. For example, themedia stream may comprise data packets and each data packet is encryptedusing the media key prior to transmission from the camera 11. If themedia key is changed, e.g. after a pre-determined length time or after apre-determined number of packets, then subsequent packets of the samemedia stream are encrypted using the updated media key. In that case theencrypted media token must be regenerated for each media key change andtransmitted again to the receiving entity 30. This approach can help tosecure communication between a receiving entity and the serviceprovider, even if the receiving entity is initially authorised todecrypt a media stream, by requiring re-authentication of the receivingentity using the regenerated encrypted media token.

9—Similarly and for same reason, the domain key can be changedperiodically. In that case a new media key and a new encrypted mediatoken must be generated for each domain key change and transmitted againto the receiving entity 30.

10—As the proposed camera media content protection scheme preserves theproperties of the content format, any intermediate entity which is notauthorized to access the unprotected camera media content can stillrecord the protected camera media content with no privacy issue. Thisrecorded camera media content can be duplicated anywhere with no privacyissue; It remains protected and accessing it requires authenticating theentity that needs to access or process the camera media content andverifications by the license provisioning service 40 as described in 5,6 and 7.

The process can uniquely protect content from the camera 11 or othermedia device and affords protection of the media regardless of thenumber of devices such as intermediate devices 20 involved in aprocessing chain.

FIG. 4 illustrates a block diagram of one implementation of a computingdevice 300 within which a set of instructions, for causing the computingdevice to perform any one or more of the methodologies discussed herein,may be executed. The computing device 300 may be used for elements ofthe system shown in FIGS. 1 and 2. In alternative implementations, thecomputing device may be connected (e.g., networked) to other machines ina Local Area Network (LAN), an intranet, an extranet, or the Internet.The computing device may operate in the capacity of a server or a clientmachine in a client-server network environment, or as a peer machine ina peer-to-peer (or distributed) network environment. The computingdevice may be a personal computer (PC), a tablet computer, a set-top box(STB), a Personal Digital Assistant (PDA), a cellular telephone, a webappliance, a server, a network router, switch or bridge, or any machinecapable of executing a set of instructions (sequential or otherwise)that specify actions to be taken by that machine. Further, while only asingle computing device is illustrated, the term “computing device”shall also be taken to include any collection of machines (e.g.,computers) that individually or jointly execute a set (or multiple sets)of instructions to perform any one or more of the methodologiesdiscussed herein.

The example computing device 300 includes a processing device 302, amain memory 304 (e.g., read-only memory (ROM), flash memory, dynamicrandom access memory (DRAM) such as synchronous DRAM (SDRAM) or RambusDRAM (RDRAM), etc.), a static memory 306 (e.g., flash memory, staticrandom access memory (SRAM), etc.), and a secondary memory (e.g., a datastorage device 318), which communicate with each other via a bus 330.

Processing device 302 represents one or more general-purpose processorssuch as a microprocessor, central processing unit, or the like. Moreparticularly, the processing device 302 may be a complex instruction setcomputing (CISC) microprocessor, reduced instruction set computing(RISC) microprocessor, very long instruction word (VLIW) microprocessor,processor implementing other instruction sets, or processorsimplementing a combination of instruction sets. Processing device 302may also be one or more special-purpose processing devices such as anapplication specific integrated circuit (ASIC), a field programmablegate array (FPGA), a digital signal processor (DSP), network processor,or the like. Processing device 302 is configured to execute theprocessing logic (instructions 322) for performing the operations andsteps discussed herein.

The computing device 300 may further include a network interface device308. The computing device 300 also may include a video display unit 310(e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)), analphanumeric input device 312 (e.g., a keyboard or touchscreen), acursor control device 314 (e.g., a mouse or touchscreen), and an audiodevice 316 (e.g., a speaker).

The data storage device 318 may include one or more machine-readablestorage media (or more specifically one or more non-transitorycomputer-readable storage media) 328 on which is stored one or more setsof instructions 322 embodying any one or more of the methodologies orfunctions described herein. The instructions 322 may also reside,completely or at least partially, within the main memory 304 and/orwithin the processing device 302 during execution thereof by thecomputing device 300, the main memory 304 and the processing device 302also constituting computer-readable storage media.

The various methods described above may be implemented by a computerprogram. The computer program may include computer code arranged toinstruct a computer to perform the functions of one or more of thevarious methods described above. The computer program and/or the codefor performing such methods may be provided to an apparatus, such as acomputer, on one or more computer readable media or, more generally, acomputer program product. The computer readable media may be transitoryor non-transitory. The one or more computer readable media could be, forexample, an electronic, magnetic, optical, electromagnetic, infrared, orsemiconductor system, or a propagation medium for data transmission, forexample for downloading the code over the Internet. Alternatively, theone or more computer readable media could take the form of one or morephysical computer readable media such as semiconductor or solid statememory, magnetic tape, a removable computer diskette, a random accessmemory (RAM), a read-only memory (ROM), a rigid magnetic disc, and anoptical disk, such as a CD-ROM, CD-R/VV or DVD.

In an implementation, the modules, components and other featuresdescribed herein (for example control unit 310 in relation to FIG. 4)can be implemented as discrete components or integrated in thefunctionality of hardware components such as ASICS, FPGAs, DSPs orsimilar devices as part of an individualization server.

A “hardware component” is a tangible (e.g., non-transitory) physicalcomponent (e.g., a set of one or more processors) capable of performingcertain operations and may be configured or arranged in a certainphysical manner. A hardware component may include dedicated circuitry orlogic that is permanently configured to perform certain operations. Ahardware component may be or include a special-purpose processor, suchas a field programmable gate array (FPGA) or an ASIC. A hardwarecomponent may also include programmable logic or circuitry that istemporarily configured by software to perform certain operations.

Accordingly, the phrase “hardware component” should be understood toencompass a tangible entity that may be physically constructed,permanently configured (e.g., hardwired), or temporarily configured(e.g., programmed) to operate in a certain manner or to perform certainoperations described herein.

In addition, the modules and components can be implemented as firmwareor functional circuitry within hardware devices. Further, the modulesand components can be implemented in any combination of hardware devicesand software components, or only in software (e.g., code stored orotherwise embodied in a machine-readable medium or in a transmissionmedium).

Unless specifically stated otherwise, as apparent from the followingdiscussion, it is appreciated that throughout the description,discussions utilizing terms such as “receiving”, “determining”,“comparing”, “enabling”, “maintaining,” “identifying,” “replacing,” orthe like, refer to the actions and processes of a computer system, orsimilar electronic computing device, that manipulates and transformsdata represented as physical (electronic) quantities within the computersystem's registers and memories into other data similarly represented asphysical quantities within the computer system memories or registers orother such information storage, transmission or display devices.

It is to be understood that the above description is intended to beillustrative, and not restrictive. Many other implementations will beapparent to those of skill in the art upon reading and understanding theabove description. Although the present disclosure has been describedwith reference to specific example implementations, it will berecognized that the disclosure is not limited to the implementationsdescribed, but can be practiced with modification and alteration withinthe spirit and scope of the appended claims. Accordingly, thespecification and drawings are to be regarded in an illustrative senserather than a restrictive sense. The scope of the disclosure should,therefore, be determined with reference to the appended claims, alongwith the full scope of equivalents to which such claims are entitled.

1. A method for securing media content in a network comprising at amedia device: receiving a domain key from a service provider; andencrypting media with a media key and encrypting the media key with thedomain key to form an encrypted media token; the method furthercomprising, at the service provider: receiving the encrypted media tokenand one or more receiving entity identifiers relating to a receivingentity; ascertaining whether the receiving entity is entitled to accessmedia from the media device; and if the receiving entity is entitled toaccess media from the media device, decrypting the encrypted media tokenusing the domain key to obtain the media key and providing the media keyto the receiving entity.
 2. A method according to claim 1, furthercomprising generating the media key at the media device.
 3. A methodaccording to claim 1 or claim 2, wherein the domain key is associatedwith a domain defining one or more media devices within the network. 4.A method according to claim 3, wherein the step of authenticating thereceiving entity comprises establishing that the receiving entity isauthorised to access media from media devices within the domainassociated with the domain key.
 5. A method according to claim 1,wherein the media device receives the domain key in a form encryptedusing one or more media device identifiers.
 6. A method according to anypreceding claim, wherein the encrypted media token comprises metadataassociated with the domain key.
 7. A method according to any precedingclaim, wherein the media device transmits the encrypted media token tothe receiving entity and wherein the service provider receives theencrypted media token from the receiving entity.
 8. A method accordingto any preceding claim, wherein the service provider receives theencrypted media token in a form encrypted using one or more receivingdevice identifiers.
 9. A method according to any preceding claim,wherein the service provider provides the media key to the receivingentity in a form encrypted using one or more receiving deviceidentifiers.
 10. A method according to any preceding claim, wherein themedia key is changed periodically.
 11. A method according to anypreceding claim, wherein the domain key is changed periodically.
 12. Amethod according to any preceding claim, wherein the media comprisesaudio and/or visual content.
 13. A method according to any precedingclaim, wherein the media device comprises a camera.
 14. A computerreadable medium comprising computer executable instructions for carryingout the method of any one of the preceding claims.
 15. A system forsecuring media content in a network comprising a media device and aservice provider, wherein: the media device is configured to: receive adomain key from the service provider; and encrypt media with a media keyand encrypt the media key with the domain key to form an encrypted mediatoken; and wherein the service provider is configured to: receive theencrypted media token and one or more receiving entity identifiersrelating to a receiving entity; ascertain whether the receiving entityis entitled to access media from the media device; and if the receivingentity is entitled to access media from the media device, decrypt theencrypted media token using the domain key to obtain the media key andprovide the media key to the receiving entity.